Skip to main content
Version: 5.1.0.0

Description

With the splitter pattern, a given message can be split into fragments. Each fragment is processed hereinafter by a single process instance. The splitting and the following processing is defined within in the same process model.

Create​

  1. Create a process model

  2. Open the panel named process, per default this panel is on the right side of the Orchestra designer window.

  3. Click on the folder activities to see its content.

  4. on "Splitter" and drag it to any place in your process model.

Icon​

splitter_icon.png

Configuration​

Label and Non functional properties​

See at common configurations for activities.

Splitting​

In this tab all settings how splittings works are done.

splitting_config.png


FieldDescription
Fragment selectionDefines how a message should be split into fragments
Split first level elements: All elements on the first level of the message are split into single pieces.
Use path selection: A simplified path expression that is used to select the result elements.
SelectionDefines a simplified path expression that is used to select the message fragments
A path expression is a repeated sequence of path-fragments, e.g., /elementA/elementB. This selection searches for all elements with the name elementB that exist within an element with the name elementA. If * is used, all element names match. Note: The simplified path selector ignores namespaces.
Also, a limited version of a recursive descent operator can be used. This allows getting all elements of the same name independent of the nesting. The path has to look like //element(/fragment)*.
Message creationDefines how the result messages are generated from the fragments
Use split element: The fragment itself is used to generate an orchestra message. This means that an orchestra message is created with the fragment as it is.
Preserve message structure: The created orchestra message has the same structure as the original message, but it contains only the fragment and the parent elements up to the root of the original message.
In both cases, the namespaces of the original message are preserved.